Presets: Fix vsInstanceVersion vendor field ignored when toolset is specified - #5075
Open
Alexander Krabler (aagor) wants to merge 1 commit into
Open
Presets: Fix vsInstanceVersion vendor field ignored when toolset is specified#5075Alexander Krabler (aagor) wants to merge 1 commit into
Alexander Krabler (aagor) wants to merge 1 commit into
Conversation
…pecified `vsInstanceVersion` vendor field at configure presets got ignored when `toolset` was specified, too. This caused the wrong VS developer environment to be loaded. The pinned version is now applied as a filter before matching the requested toolset, making `vsInstanceVersion` and `toolset` together useful. Closes microsoft#5074.
Author
|
@microsoft-github-policy-service agree company="KUKA" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
vsInstanceVersionvendor field at configure presets got ignored whentoolsetwas specified, too.This caused the wrong VS developer environment to be loaded.
The pinned version is now applied as a filter before matching the requested toolset, making
vsInstanceVersionandtoolsettogether useful.Closes #5074.